Floppyshop 2/Floppyshop - 2.zip/Floppyshop - 2.iso/diskmags/0022-3.564/dmg-0049/416.txt

Text File | 1997-04-16 | 19KB | 499 lines

Info-Atari16 Digest   Friday, August 25, 1989   Volume 89 : Issue 416

This weeks Editor: Bill Westfield

Today's Topics:

                                 OOps
                              UUCP stuff
                                  TT
                           Sozobon compiler
                  Re: Re~2: New Atari 68030 Machines
             Re: NetHack3 binary needed for Atari 1040 ST
                     digital writing/drawing pad
                 comp.binaries.atari.st intro article

----------------------------------------------------------------------

Date: 21 Aug 89 06:58:07 GMT
From: mailrus!um-math!sharkey!itivax!m2-net![e-mail]  (Eric
 Doggett)
Subject: OOps
To: [e-mail]

The first line on that should have read...

I am looking for a PD UUCP package that would work on an...

------------------------------

Date: 21 Aug 89 06:51:25 GMT
From: mailrus!um-math!sharkey!itivax!m2-net![e-mail]  (Eric
 Doggett)
Subject: UUCP stuff
To: [e-mail]

IBM Emulator, or the ST itself, I have tried fsuucp, can't seem to get it
to do anything but sit there and tick me off, anyone know where to find one?

         cardiology.ummc.umich.edu!m-net!moses
         cardiology.ummc.umich.edu!sharkey.cc.umich.edu!spirit!wybbs!moses

All help would be appreciated greatly...

------------------------------

Date: Mon, 21 Aug 89 22:04:07 bst
From: [e-mail]
To: [e-mail]

help

------------------------------

Date: 21 Aug 89 22:06:42 GMT
From: blake![e-mail]  (Moja Fritzah)
Subject: TT
To: [e-mail]

DOes anybody know what the RAM speed is in the TT?

Will it be possible to pop in a faster 030 chip?  040?


-kevin
[e-mail]

------------------------------

Date: 21 Aug 89 14:41:19 GMT
From: mcvax!ukc!edcastle![e-mail]  (Kevin "tkld" Davidson)
Subject: Sozobon compiler
To: [e-mail]

Can anyone tell me what the latest version of Sozobon CC is ?
Has hcc been upgraded to accept this sort of construct:

#if defined(MSDROSS) || defined(TOS)

int foo, bar, fred;

#endif

If not I'll have a go at putting it in myself - I'd guess it would have to
work like sizeof(...), and expr.c would replace it with a constant expression
for p_if().

I found stuff like this trying to compile the recently posted nethack 3.0f
on a sun. I have sozobon set up as a cross compiler, but it took me a couple
of days to get rid of most of the assumptions that sizeof(int) == sizeof(short)
(I even managed to find a line `#define short int' in one .h file !)
This *had* to be a deliberate attempt to get back at mainframe programmers
who *always* assume sizeof(int)==sizeof(long) :-)

Howzabout a complete ban of int fields in structures ? :-) :-)
Or get rid of int :-) :-) :-)


Has anyone thought about adding the const and inline storage classes ?
I haven't looked to see how much work this would be (#define inline void
just doesn't satisfy me :-)


I'll do the work if nobody else is interested - looks like fun, but I *hate*
reinventing the wheel (except when the supplied wheel is reeeaaally ugly)

--

        .Kevin.        <[e-mail]>
                       <[e-mail]>

------------------------------

Date: 21 Aug 89 20:21:07 GMT
From: att!laidbak![e-mail]  (Jonathan E. Quist)
Subject: Re: Re~2: New Atari 68030 Machines
To: [e-mail]

In article <[e-mail]> [e-mail] (Bob Breum) writes:

>run multiple DOS sessions under UNIX?  Now _that_ would be the best of
>all possible worlds: Several UNIX windows, including a couple of TOS
>sessions and a couple of MS-DOS sessions mixed in with standard UNIX
>tasks.


Somehow, Jackson Pollack comes to mind.

Some call it art, some don't.


jeq

------------------------------

Date: 22 Aug 89 00:32:01 GMT
From:
 agate!bionet!csd4.csd.uwm.edu!mailrus!jarvis.csri.toronto.edu!utgpu!watmath!jul
ian!uwovax![e-mail]
Subject: Re: NetHack3 binary needed for Atari 1040 ST
To: [e-mail]

In article <[e-mail]>, [e-mail] (Cris Fuhrman)
 writes:
> Can anyone tell me if there's a pre-compiled binary for NetHack 3.0
> available via anonymous ftp for a single-drive Atari 1040 ST?

One will be posted Real Soon Now, as soon as the flood of NetHack bug fixes
slows to a trickle.
--
Eric R. Smith                      email:
Dept. of Mathematics               [e-mail]
University of Western Ontario      [e-mail]
London, Ont. Canada N6A 5B7    (a shared mailbox: put my name on
ph: [phone]              the Subj: line, please!)

------------------------------

Date: 22 Aug 89 03:19:53 GMT
From: ogccse!blake![e-mail]  (Moja Fritzah)
Subject: digital writing/drawing pad
To: [e-mail]

Does one exist for the ST?

-kevin
[e-mail]

------------------------------

Date: 21 Aug 89 23:02:17 GMT
From: sunfedcomm!grapevine!panarthea.sun.com![e-mail]  (Steven Grimm)
Subject: comp.binaries.atari.st intro article
To: [e-mail]

I just added some stuff to this.  As always, please inform me of any errors
or possible improvements.  (?roff source is available...)

---
This message is a figment of your imagination.  Any opinions are yours.
Steven Grimm            Moderator, comp.
[e-mail]          ...!sun!sgrimm


--- cut here ---







             HOW TO USE COMP.BINARIES.ATARI.ST

                      by Steven Grimm

                Last update: August 21, 1989




_✓1.  _✓W_✓h_✓a_✓t _✓a_✓r_✓e _✓b_✓i_✓n_✓a_✓r_✓i_✓e_✓s?

     Binaries are files that contain information other  than
normal  text.   Usually,  a binary that is posted to the net
will contain executable (program) files.  Binaries are  dis-
tinct  from _✓s_✓o_✓u_✓r_✓c_✓e_✓s, which are the human-readable text files
that are interpreted by  a  computer  and  used  to  produce
binaries.   Sources  can  be modified with relatively little
effort, and are usually pretty easy to read.   Binaries  are
not intended to be viewed by a human.

_✓1._✓1.  _✓U_✓u_✓e_✓n_✓c_✓o_✓d_✓i_✓n_✓g

     The programs which transfer network news messages  (and
electronic  mail)  are not always capable of handling a pure
binary file.  They are designed to handle textual  messages,
and the odd symbols and characters in a binary cause them to
become confused, and often to mangle the binaries.  To avoid
this  problem, a method called _✓u_✓u_✓e_✓n_✓c_✓o_✓d_✓i_✓n_✓g is used.  Uuencod-
ing translates a binary file into text characters,  so  that
the  news  and  mail  transport programs won't mess up.  The
disadvantages are that uuencoded files are about 30%  bigger
than  the raw binary files they represent, and that you have
to go through one extra step to get the binaries to work  on
your computer.

_✓1._✓2.  _✓A_✓r_✓c_✓h_✓i_✓v_✓e_✓s _✓o_✓r "_✓a_✓r_✓c _✓f_✓i_✓l_✓e_✓s"

     Usually, a program will need more than one file to work
properly.   The extra files might be data files, help files,
or maybe some instructions for the user.  In order to easily
package  multiple  files together in one binary file, a pro-
gram called "arc" (short for "archiver") is used.  Arc  also
compresses  all  the  files as it packages them, so that the
arcfile take up less disk space  (and  takes  less  time  to
download!)  than  it  would if its contents were just thrown
together.

     To confuse matters even more,  a  new  archive  program
called  "zoo"  can  also be used to achieve the same effect.
Zoo is superior to arc in some respects,  slightly  inferior
in  others.   Unfortunately,  you can't unpack a zoo archive
with arc, or vice versa.










Using Binaries                                           -2-


_✓1._✓3.  _✓U_✓S_✓E_✓N_✓E_✓T _✓a_✓r_✓t_✓i_✓c_✓l_✓e_✓s

     The USENET has groups designed especially for transmis-
sion  of  binary  files.   They are usually called something
like "comp.binaries.x," where x is the type of machine  that
the programs will run on.  For Atari ST owners, the group to
watch  is  comp.binaries.atari.st.   Most  of  the  binaries
groups  (including  the Atari binaries group) are _✓m_✓o_✓d_✓e_✓r_✓a_✓t_✓e_✓d,
which means that you can't send a program directly to every-
one  on  the  network.   Instead,  you send it to someone in
charge of the group (the _✓m_✓o_✓d_✓e_✓r_✓a_✓t_✓o_✓r),  who  makes  sure  that
your program works and contains the proper documentation (or
that the lack of documentation is announced), and that  it's
in  the  correct  format  to  be sent out to the rest of the
USENET.

     One of the restrictions of the USENET is that  articles
can  only  be  a certain length.  If a binary is longer than
that, it must be split up into several parts, each no longer
than  45000 bytes or so.  This introduces yet another obsta-
cle to people who want to transform the articles into a use-
ful  form,  but  it  can't really be helped until the USENET
starts  running  much  more   advanced   news   transmission
software.   Also,  some  particularly  long  programs may be
posted over the course of several days;  otherwise  the  net
would  be  overloaded with lots of huge messages, and people
would complain.

     USENET binaries are grouped into _✓v_✓o_✓l_✓u_✓m_✓e_✓s, each contain-
ing  about  100  articles.   This is to make life easier for
people who are trying to keep track of which  articles  have
been  posted.   When  a new volume is started, the moderator
will usually post introductory articles, including a list of
previously published articles.

_✓2.  _✓H_✓o_✓w _✓d_✓o _✓I _✓g_✓e_✓t _✓b_✓i_✓n_✓a_✓r_✓i_✓e_✓s?

     There are two ways to get binaries: first,  by  reading
the  USENET  newsgroup  comp.binaries.atari.st; you will see
new articles within a week (usually much less) of  the  time
they  were  sent out by the moderator.  If, for some reason,
your site doesn't receive comp.binaries.atari.st, or if  you
want  to  look  through  previously  posted  articles,  site
panarthea.ebay.sun.com has all the binaries  stored  in  its
archives.

     The other way to get binaries is to request  them  from
panarthea's archive server.  The archive server is a program
that intercepts incoming mail messages and  looks  for  com-
mands  inside  them.   You can tell it to list the available
binaries, give you help,  or  send  whichever  files  you're
interested  in.   The requested files will be mailed to you.
One thing to be  careful  of  is  that  multi-part  postings
aren't  placed  in  the  archives until all their parts have









Using Binaries                                           -3-


been sent out to the USENET at large.  This  is  to  prevent
people  from  requesting all 99 parts of a program the first
day it appears, thus overloading the net and  defeating  the
purpose of piece-by-piece posting.

     To find out more about the archive server, send a  mail
message    containing    the   word   "help"   to   archive-
[e-mail]  Talk to an  administrator  at
your  site  if that mail address doesn't work.  If you don't
get any response from the archive server within a few  days,
something      may      be      wrong;     mail     archive-
[e-mail] to report the problem.

     There  are  other   archive   sites,   too,   such   as
terminator.cc.umich.edu;    they   contain   most   of   the
comp.binaries.atari.st software as well as  some  additional
programs  that  have  not  appeared on the newsgroup.  (Some
sites, such  as  terminator,  also  offer  something  called
"anonymous  ftp"  if  you're  on  the  Internet.   Say  "ftp
terminator.cc.umich.edu",   and   if   you   connect,    use
"anonymous"  for  a  username, and your username for a pass-
word.  See the ftp  documentation  at  your  site  for  more
information.)   A  recent,  but  possibly incorrect, list of
alternate archive sites appears at the end of this  article.
Please send me mail if you know of any that aren't mentioned
here, or if my list is incorrect.

     Panarthea also offers an "auto-index" service, for peo-
ple  who  don't  have  access  to the USENET groups.  If you
request autoindex service, you will receive  copies  of  the
archive-server's  index  files  for the binaries and sources
groups whenever new files are added.  Note that if your site
gets  comp.binaries.atari.st, requesting autoindex is point-
less and a waste of net bandwidth.  Send mail to  autoindex-
[e-mail] if you'd like to sign up.

_✓3.  _✓H_✓o_✓w _✓d_✓o _✓I _✓d_✓e_✓c_✓o_✓d_✓e _✓t_✓h_✓e
 _✓b_✓i_✓n_✓a_✓r_✓i_✓e_✓s?

     As stated above, turning binaries from USENET  articles
into a more useful form can be a multi-step process.  At the
least, you will need the uudecode program;  it  is  standard
software on most UNIX|✓- systems and is available in a  couple
of forms on the Atari.  Versions for other operating systems
do exist, and can certainly be written with  little  effort.
Arc  is  available for UNIX and other operating systems, but
is not standard software.  In any case,  you  will  want  at
least arc on your Atari.

     A version of uudecode written in ST BASIC is  available
in  panarthea's  archives (see above).  It is in volume 1 of
the  comp.sources.atari.st  directory  (note   that   that's
_________________________
|✓- UNIX is a trademark of Bell Laboratories.










Using Binaries                                           -4-


_✓s_✓o_✓u_✓r_✓c_✓e_✓s and not binaries).  Once you have that,  you  should
get the files "arc," "arcdoc," and "uucode" from volume 1 of
the binaries directory.  They contain the arc  program  men-
tioned earlier, its documentation, and a much better, faster
version of the uudecode program.

     Use the BASIC  program  to  uudecode  the  two  encoded
files;  then  use  arc  to  unpack  the  better  version  of
uudecode.  (Arc is documented in "arcdoc.")   Note  that  if
you're  reading news/receiving mail on a computer (such as a
UNIX system) that already has uudecode, you can skip most of
this;  you  will  probably  just want to uudecode arc there,
then download it (using kermit,  xmodem,  or  your  favorite
transfer  protocol  -  consult your site's administrator and
your Atari communication package's  documentation  for  more
information.   Remember  to use binary mode when downloading
arc files!)

     So far, everything has been small enough to fit in  one
piece,  but  you will almost certainly want to try something
larger eventually.  The Atari "uud"  program  (whose  source
code,  also  suitable  for  compilation  on UNIX systems, is
available in the  sources  archive)  is  capable  of  easily
decoding  multi-part  uuencoded files.  Near the top of each
part (except the first) will be a line like

        begin part c foobar.uac


     Rename each file (except part 1,  which  can  be  named
"part01" or just about anything else) to the name at the end
of this "begin" line, in this case "foobar.uac".   Then  run
uud  on the file containing part 1; it contains instructions
to cause uud to look for the other parts.   If  you  have  a
text  editor or a UNIX style cat program, you can just stick
all the parts together in order and run uud on the resulting
(big)  file;  it  will  try to go on in the first file if it
can't find the next part in a separate file.

     If you don't have uud or would prefer  to  decode  your
binaries  on  your  larger  news  computer, the procedure is
somewhat more complex.  Plain vanilla uudecode doesn't  know
about  multi-part  uuencoded  files,  so you have to fool it
into thinking that everything is in one part.  First,  stick
all  the  parts  together  (using  cat  on  UNIX).  Edit the
resulting file.  Now remove all the extraneous lines of text
in  between  the  parts  --  this includes mail headers, any
text, lines of the form "include foobar.uad," "table"  lines
and  the  lists  of  characters  following them, and "begin"
lines other than the one at the beginning of part  1.   Once
you  have  converted all the parts into a big uuencoded mass
(with no blank lines!), the regular  uudecode  program  will
work.










Using Binaries                                           -5-


     Obviously, this is  something  of  a  hassle,  and  the
recommended procedure is to try to install uud on your large
computer.  You'll usually want to  minimize  the  amount  of
data  you  have  to  send  to  your Atari, since you'll most
likely be downloading it at a relatively low speed, and  the
uudecoded .arc file is the smallest thing you can download.

     Zoo is available from the archives.  It  is  simple  to
use; refer to the documentation included in zoobin.arc (yes,
you need to use arc to extract zoo!) for  more  information.
The uudecoding process is the same for zoo and arc files.

     Most  archives  contain  documentation;  refer  to  the
instructions in a specific program for usage information and
the like.  If you have problems with a  particular  program,
send  mail  to  the  submitter  (listed near the top of each
part.)  The moderator doesn't have time to become very fami-
liar with all the programs that are posted, so the submitter
will probably be much more helpful.


_✓4.  _✓L_✓i_✓s_✓t _✓o_✓f _✓a_✓r_✓c_✓h_✓i_✓v_✓e _✓s_✓i_✓t_✓e_✓s

     Note: I have not verified these, so this  list  may  be
wrong.   Mail  servers  usually  respond  to the word "help"
alone in a mail message.

Address                        Type   Comments
_________________________________________________________________
terminator.cc.umich.edu        ftp    Mail server may also exist
him1.cc.umich.edu              ftp    cd to pc7: directory
dsrgsun.ces.cwru.edu           ftp    GNU and Minix archives also
xanth.cs.odu.edu               ftp
[e-mail]            mail
[e-mail]    mail
[e-mail]   uucp   Ask your site administrator

------------------------------

End of Info-Atari16 Digest
**************************
-------